Skip to content

Remove notify-moe from response#914

Open
BrutuZ wants to merge 1 commit intobeeequeue:mainfrom
BrutuZ:remove-notifymoe
Open

Remove notify-moe from response#914
BrutuZ wants to merge 1 commit intobeeequeue:mainfrom
BrutuZ:remove-notifymoe

Conversation

@BrutuZ
Copy link
Contributor

@BrutuZ BrutuZ commented Feb 19, 2026

Separating from and per request on #906

What changed:

Removed notify-moe from the response since it was removed upstream both manami (manami-project/manami#1066) and consequently from Fribb's anime-list (Fribb/anime-lists#23 (comment)) since Fribb uses manami's anime-offline-database to generate the list we use to populate the database

Copy link
Owner

@beeequeue beeequeue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while i do agree with this in a sense of proper code hygiene, im also not sure if removing it is a good idea since it would break backwards compatibility for anyone expecting the field to exist.

but is there actually anyone that uses the notify-moe fields? :^)

maybe it's just better to keep the field and always return null for it?

@BrutuZ
Copy link
Contributor Author

BrutuZ commented Feb 25, 2026

That is a fair assessment, one I also considered. Both the "does anyone use this?" and "shouldn't code always be safe and account for both field nullability and absence?" angles.

Your call, I promise I won't be offended if you decide to keep the field and close the PR 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants